Update README.md for WordPress 6.9/7.0 changes#165
Update README.md for WordPress 6.9/7.0 changes#165itsgajendraSingh wants to merge 4 commits intoWordPress:trunkfrom
Conversation
Fixes WordPress#160. Relates to WordPress#150 and WordPress#101.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
There was a problem hiding this comment.
Pull request overview
This PR updates the README.md documentation to reflect changes in WordPress 6.9/7.0 compatibility, specifically addressing the merging of the Abilities API into WordPress core, the archiving of the WordPress/abilities-api repository in February 2026, and the inclusion of the MCP Adapter in WordPress 7.0 core.
Changes:
- Added WordPress version requirement (>= 6.8, with 6.9+ recommended and 7.0+ bundled) and updated Abilities API documentation to reference core dev notes instead of the archived plugin repository
- Updated
composer requirecommand to remove the archivedwordpress/abilities-apipackage with conditional installation notes for WordPress 6.8 - Removed
WordPress/abilities-apifrom.wp-env.jsonexample with a note for WordPress 6.8 compatibility - Clarified that the
meta.mcp.publicflag is required for abilities to appear on the default MCP server, with updated code examples - Updated STDIO transport documentation from "Testing Only" to "Local Development" and added explanation of the
@automattic/mcp-wordpress-remoteproxy - Added WordPress.com MCP support information and v0.3.0 migration guide reference
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## trunk #165 +/- ##
============================================
+ Coverage 88.04% 88.25% +0.21%
- Complexity 1236 1243 +7
============================================
Files 54 54
Lines 4022 4035 +13
============================================
+ Hits 3541 3561 +20
+ Misses 481 474 -7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…cute tools Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…tocol version Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
galatanovidiu
left a comment
galatanovidiu
left a comment
There was a problem hiding this comment.
Thanks for the PR and for catching several real gaps in the README. There are a few things that need fixing before this can be merged.
Core inclusion claim (blocking)
The MCP Adapter is not part of WordPress core. It's a standalone package/plugin. References to it being "bundled in core" or "shipped in WordPress 7.0" need to be removed. This appears in:
- Dependencies:
7.0+ includes the MCP Adapter in core - Installation note:
On WordPress 7.0+, the MCP Adapter itself is bundled in core - PR description:
the MCP Adapter shipped in WordPress 7.0 core (April 2026) - The "client-side JavaScript counterpart" paragraph and link are tied to the same claim
The Abilities API is in core since 6.9, but the MCP Adapter itself is a separate standalone package/plugin. These are two different things.
Protocol versions (non-blocking)
The PR mentions support for 2025-06-18 and 2025-11-25, but McpVersionNegotiator also supports 2024-11-05. Either list all three or use something like "supports multiple MCP protocol versions" without implying the list is exhaustive.
What's good here
The meta.mcp.public documentation, STDIO relabeling to "Local Development", WordPress.com MCP note, v0.3.0 migration link, abilities-api removal from default install, and the proxy explanation are all accurate and useful. I'd like to keep those.
Fixes #164. Extends #150. Related: #101.
Updates the README to reflect changes since the Abilities API merged into WordPress 6.9 core (Dec 2025), the WordPress/abilities-api repo was archived (Feb 2026), and the MCP Adapter shipped in WordPress 7.0 core (April 2026).
Changes
composer requirecommand includeswordpress/abilities-api(archived package)>= 7.4.wp-env.jsonexample includesWordPress/abilities-apiin plugins arraymeta.mcp.publicrequirementmeta.mcp.publicflag — ability won't appear on default server without it@automattic/mcp-wordpress-remoteproxy does